Repository navigation
Expose read-only runtime discovery for consumers - #5
Open
graywolf336 wants to merge 1 commit into
Open
graywolf336 wants to merge 1 commit into
graywolf336 wants to merge 1 commit into
Conversation
Contributor
Author
|
Matching-contract native verification now passed using the existing Atomic 0.22.1 archive (its full embedded protobuf descriptor matches this consumer's pinned v0.22.0 fingerprint): 25 tests passed across bridge, status, vault, and public loading suites, including worker threads, repository isolation, native mutations/queries, and retry/cache behavior. The earlier 0.20.0 rejection was an environment mismatch, not a regression. TypeScript build, the 27 independent runtime/build tests, and the public metadata-only discovery smoke also passed. Sherpa vendors commit ec31722 for its fresh-workspace onboarding fix. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expose the existing resolveRuntime function at the public entry point so Sherpa can discover missing Atomic installations in Git-only workspaces without native loading or CLI execution. No resolver, protobuf, fingerprint, or native contract changes. Document the metadata-only boundary versus full first-operation validation. TypeScript build and public-entry smoke passed; 30 existing tests passed. Twenty native integration tests rejected the host's installed Atomic 0.20.0 contract, as expected for this v0.22.0 consumer; matching-runtime verification will be recorded separately.